Remote user interface

ABSTRACT

Target electronic devices can be remotely controlled using a personal electronic device are disclosed. The personal electronic device can identify target devices that are responsive to remote control. The personal electronic device displays graphical user interface objects that, when selected, cause the personal electronic device to instruct the target electronic device to perform an operation.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/805,403, entitled “REMOTE USER INTERFACE” filed Jul. 21, 2015 whichclaims the benefit of priority of Provisional Patent Application No.62/027,145, entitled “REMOTE USER INTERFACE,” filed Jul. 21, 2014; U.S.Provisional Patent Application No. 62/027,764, entitled “REMOTE USERINTERFACE,” filed Jul. 22, 2014; and U.S. Provisional Patent ApplicationNo. 62/129,798, entitled “REMOTE USER INTERFACE,” filed Mar. 7, 2015.The content of these applications is hereby incorporated by reference intheir entirety for all purposes.

This application relates to the following applications: InternationalPatent Application Serial No. PCT/US2013/040061, entitled “Device,Method, and Graphical User Interface for Displaying User InterfaceObjects Corresponding to an Application,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/069483, entitled“Device, Method, and Graphical User Interface for Transitioning BetweenTouch Input to Display Output Relationships,” filed Nov. 11, 2013; andU.S. Provisional Patent Application Ser. No. 62/026,532, “Raise GestureDetection in a Device,” filed Jul. 18, 2014. The content of theseapplications are hereby incorporated by reference in their entirety.

FIELD

The disclosed examples relate generally to user interfaces of electronicdevices.

BACKGROUND

Consumers often own multiple electronic devices. Such electronic devicesmay be portable devices like cellular phones, tablet computers, laptops,digital audio players, and so forth. Such electronic devices may also behome electronics like audio-visual equipment, home security equipment,home automation equipment, appliances, and so forth. Such electronicdevices may also be integrated with equipment not traditionally labeledas electronic devices. For example, such electronic devices may includetelematics equipment that is integrated with an automobile.

SUMMARY

User interfaces for remotely controlling target electronic devices usinga personal electronic device with a touch-sensitive display aredisclosed. In some examples, at an electronic device with atouch-sensitive display, where the touch-sensitive display comprises oneor more sensors to detect the intensity of contacts with thetouch-sensitive display, a plurality of icons representing applications,including an icon representing a remote control application, aredisplayed. A first contact on the touch-sensitive display at a locationof the icon is received. The electronic device determines whether atarget device out of a plurality of target devices is responsive toremote control. In response to the first contact and a determination ofthe target device being responsive to remote control, the electronicdevice displays a first plurality of remote controls for the targetdevice. Further, while displaying the first plurality of remotecontrols, the electronic device receives a second contact on thetouch-sensitive display, the second contact having a maximum intensity.In response to receiving the second contact and a determination that themaximum intensity is below a threshold intensity, the electronic deviceinstructs the target device to perform an operation; and in response toreceiving the second contact and a determination that the maximumintensity is above the threshold intensity, the electronic devicedisplays a second plurality of remote controls for the first targetdevice.

In some examples, the electronic device displays a user interface objecton the touch-sensitive display of the electronic device, where thedisplayed user interface object represents a remote control application.The electronic device receives data representing a contact on thedisplayed user interface object, and identifies a target electronicdevice that is responsive to remote control. In response to receivingthe data representing the contact, the electronic device displaysgraphical user interface objects for controlling operations of theidentified target electronic device.

In some examples, when none of the target electronic devices of theplurality of target electronic devices is responsive to remote control,the electronic device displays a plurality of graphical user interfaceobjects representing the plurality of target electronic devices.Restated, in response to a determination that no target electronicdevice is responsive to remote control, the electronic device displays aplurality of graphical user interface objects that represent theplurality of target electronic devices.

In some examples, the electronic device receives first data representinga first contact at a location on the touch-sensitive display, the firstcontact having a maximum intensity below a predetermined thresholdintensity, and the location is associated with an operation of a targetelectronic device. In response to the first contact (which is arelatively lighter touch), the device sends an instruction to the targetelectronic device instructing the target electronic device to perform anoperation. The electronic device then additionally receives second datarepresenting a second contact on the display, the second contact havinga maximum intensity above the threshold intensity. In response to thesecond contact (which is a relatively harder touch), the electronicdevice displays a user interface for registering (e.g., pairing) a newtarget electronic device with the remote control application.

In some examples, an intermediate device relays instructions from theelectronic device that is running the remote control application to thetarget electronic device that is being remotely controlled. That is, theelectronic device sends data to an intermediate electronic device, wherethe data represents an instruction instructing the target electronicdevice to perform the operation, and an instruction is then communicatedby the intermediate electronic device to the target electronic device.

In some examples, the target electronic device is responsive to remotecontrol when the target electronic device is executing an applicationhaving an operation that can be requested using the remote controlapplication.

In some examples, the electronic device obtains data representing aplurality of target devices, displays a user interface objectrepresenting a remote control application, and receives datarepresenting a selection on the displayed user interface object. Theelectronic device determines whether the number of target devicesexceeds a threshold, and in accordance with a determination that thenumber exceeds the threshold, the electronic device displays a pluralityof graphical user interface objects representing categories of targetdevices, in response to receiving the data, and in accordance with adetermination that the number does not exceed the threshold, theelectronic device a plurality of graphical user interface objectsrepresenting the plurality of target devices, in response to receivingthe data.

In some examples, the electronic device determines the location of atarget device relative to the electronic device; and displays, on thetouch-sensitive display, a user interface object representing the targetdevice. The target device is nearby and the display position of the userinterface object, on the touch-sensitive display, is based on thelocation of the target device relative to the electronic device in someexamples.

In some examples, the electronic device displays a user interface objectrepresenting a remote control application on the touch-sensitive displayof the electronic device, receives first data representing a zoomfunction on the displayed user interface object; and in response toreceiving the first data representing the zoom function, displays anaffordance including indication of nearby target devices capable ofbeing remotely controlled.

In some examples, the electronic device receives data representing afirst movement of a rotatable input device; and in response to receivingthe data representing the first movement, displays only a subset of theplurality of graphical user interface objects, where the displayedsubset of graphical user interface objects includes the iconrepresenting the remote control application, and displays an affordanceincluding indication of nearby target devices capable of being remotelycontrolled.

In some examples, the electronic device identifies a target device thatis responsive to remote control out of a plurality of target devices,detects a raise gesture based on detected motion of the electronicdevice; and, in response to detecting the raise gesture, instructs thetarget device to perform an operation.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIG. 6 illustrates an exemplary personal electronic device.

FIG. 7 illustrates an exemplary user interface.

FIG. 8 illustrates an exemplary user interface.

FIG. 9 illustrates an exemplary user interface.

FIG. 10 illustrates an exemplary user interface.

FIG. 11 illustrates an exemplary user interface.

FIG. 12 illustrates an exemplary user interface.

FIG. 13 illustrates an exemplary user interface.

FIG. 14A illustrates an exemplary user interface.

FIG. 14B illustrates an exemplary user interface.

FIG. 15A illustrates an exemplary process for remotely controlling atarget electronic device.

FIG. 15B illustrates an exemplary process for remotely controlling atarget electronic device.

FIG. 16 illustrates an exemplary process for remotely controlling atarget electronic device.

FIG. 17 illustrates an exemplary process for remotely controlling atarget electronic device.

FIG. 18A illustrates an exemplary process for remotely controlling atarget electronic device.

FIG. 18B illustrates an exemplary process for remotely controlling atarget electronic device.

FIG. 19 illustrates an exemplary computing system.

FIG. 20 illustrates an exemplary communication path.

FIG. 21A illustrates an exemplary user interface.

FIG. 21B illustrates an exemplary user interface.

FIG. 22A illustrates an exemplary user interface.

FIG. 22B illustrates an exemplary user interface.

FIG. 23 illustrates exemplary components of an electronic device.

FIG. 24 illustrates an exemplary process for remotely controlling atarget electronic device.

FIG. 25 illustrates a function block diagram of an electronic device inaccordance with some embodiments.

FIG. 26 illustrates a function block diagram of an electronic device inaccordance with some embodiments.

FIG. 27 illustrates a function block diagram of an electronic device inaccordance with some embodiments.

FIG. 28 illustrates a function block diagram of an electronic device inaccordance with some embodiments.

FIG. 29 illustrates a function block diagram of an electronic device inaccordance with some embodiments.

FIG. 30 illustrates a function block diagram of an electronic device inaccordance with some embodiments.

FIG. 31 illustrates a function block diagram of an electronic device inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

As discussed above, consumers often own multiple electronic devices. Itis desirable for a user to be able to remotely control these electronicdevices. It is also desirable for the device (i.e., the “remotecontrol”) that is used to remotely control these electronic devices tobe portable and readily accessible. It is also desirable for the remotecontrol to support remote control of various electronic devices whilemaintaining a physical form factor that promotes usability.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for remote control of anelectronic device. FIGS. 6-14 and 21A-22B illustrate exemplary userinterfaces for performing examples of remote control described herein.The user interfaces in the figures are also used to illustrate theprocesses described below, including the processes in FIGS. 15A-18B and24.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes one or more computer-readable storagemediums. The computer-readable storage mediums are optionally tangibleand non-transitory. The computer-readable storage mediums are optionallytransitory. Memory 102 optionally includes high-speed random accessmemory and optionally also includes non-volatile memory, such as one ormore magnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11 ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionallyretrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer (notshown) and a GPS (or GLONASS or other global navigation system) receiver(not shown) for obtaining information concerning the location andorientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module,    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo!Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150is, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatis, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces is, optionally, implemented ondevice 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404,    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 are optionally labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, and InternationalPatent Application Serial No. PCT/US2013/069483, titled “Device, Method,and Graphical User Interface for Transitioning Between Touch Input toDisplay Output Relationships,” filed Nov. 11, 2013, each of which ishereby incorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 may be a rotatable input device or a depressible androtatable input device, for example. Input mechanism 508 is, optionally,a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 1500-1850 (FIGS.15A-18B) and process 2400 (FIG. 24). The computer-executableinstructions can also be stored and/or transported within anynon-transitory computer-readable storage medium for use by or inconnection with an instruction execution system, apparatus, or device,such as a computer-based system, processor-containing system, or othersystem that can fetch the instructions from the instruction executionsystem, apparatus, or device and execute the instructions. For purposesof this document, a “non-transitory computer-readable storage medium”can be any medium that can tangibly contain or store computer-executableinstructions for use by or in connection with the instruction executionsystem, apparatus, or device. The non-transitory computer-readablestorage medium can include, but is not limited to, magnetic, optical,and/or semiconductor storages. Examples of such storage include magneticdisks, optical discs based on CD, DVD, or Blu-ray technologies, as wellas persistent solid-state memory such as flash, solid-state drives, andthe like. Personal electronic device 500 is not limited to thecomponents and configuration of FIG. 5B, but can include other oradditional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). Forexample, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation) rather than being used todetermine whether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, be characterized relative to one or more intensitythresholds, such as a contact-detection intensity threshold, a lightpress intensity threshold, a deep press intensity threshold, and/or oneor more other intensity thresholds. In some embodiments, the light pressintensity threshold corresponds to an intensity at which the device willperform operations typically associated with clicking a button of aphysical mouse or a trackpad. In some embodiments, the deep pressintensity threshold corresponds to an intensity at which the device willperform operations that are different from operations typicallyassociated with clicking a button of a physical mouse or a trackpad. Insome embodiments, when a contact is detected with a characteristicintensity below the light press intensity threshold (e.g., and above anominal contact-detection intensity threshold below which the contact isno longer detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

FIG. 6 illustrates exemplary personal electronic device 600 (hereafterdevice 600) that can have a remote control software application thatpermits electronic device 600 to remotely control other electronicdevices. Device 600 includes body 602. In some examples, device 600 hastouch-sensitive display screen (hereafter touchscreen) 604. Touchscreen604 can include a display device, such as a liquid crystal display(LCD), light-emitting diode (LED) display, organic light-emitting diode(OLED) display, or the like, positioned partially or fully behind or infront of a touch sensor panel implemented using any desired touchsensing technology, such as mutual-capacitance touch sensing,self-capacitance touch sensing, resistive touch sensing, projection scantouch sensing, or the like.

Touchscreen 604 can allow a user to perform various functions bytouching or hovering near the touch sensor panel. The user may makecontact with touchscreen 604 using any suitable object or appendage,such as a stylus, a finger, and so forth. In some examples, device 600is designed to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based inputs due to the largerarea of contact of a finger on the touchscreen. In some examples, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

Touchscreen 604 can display graphical user interface objects. Examplesof such graphical user interface objects include images, video, text,and other graphics. As used here, the term “icon” refers to a graphicaluser interface object—such as an image—that provides a visual indicationof a device feature and optionally, when activated, initiates thatfeature. Also, as used here, the term “affordance” refers to a graphicaluser interface object—such as an image—and/or its content—such as textwithin the image.

In some examples, touchscreen 604 has one or more intensity sensors (notshown) for detecting intensity of contacts being applied. The one ormore intensity sensors of touchscreen 604 can provide output data thatrepresents the intensity of contacts. The user interface of device 600can respond to contacts based on their intensity, meaning that contactsof different intensities can invoke different user interface operationson device 600. As used here, the term “intensity” of a contact ontouchscreen 604 refers to the force or pressure (force per unit area) ofa contact (e.g., a finger) on the touchscreen.

In some examples, touchscreen 604 does not have the above-describedintensity sensors, rather, device 600 uses a substitute (proxy) for theforce or pressure of a contact on touchscreen 604. In these examples,the size of the contact area detected on the touchscreen 604 and/orchanges thereto, the capacitance of the touchscreen 604 proximate to thecontact and/or changes thereto, and/or the resistance of the touchscreen604 proximate to the contact and/or changes thereto can be used as asubstitute for the force or pressure of the contact on touchscreen 604.These substitute measurements for contact force or pressure may be useddirectly to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is described in units corresponding tothe substitute measurements). Alternatively, these substitutemeasurements for contact force or pressure may be converted to anestimated force or pressure and the estimated force or pressure may thenbe used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure).

In some examples, regardless of whether touchscreen 604 has theabove-described intensity sensors, device 600 can optionally communicatewith a stylus having a pressure-sensitive tip that detects and providesdata regarding the intensity of the stylus's contact on device 600,particularly touchscreen 604.

In some examples, device 600 has one or more input mechanisms 606 and608. Input mechanisms 606 and 608, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some examples, device 600 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 600 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth.

1. Remote Control User Interface

FIG. 7 shows exemplary user interface screen 700 that device 600 candisplay on touchscreen 604. Screen 700 can be, for example, a homescreen that appears when the display of device 600 is powered on, orthat appears in response to user input on device 600. Screen 700 hasicons 702, 704, 706, 708, and 710. These icons correspond to softwareapplications that are available on device 600. A user can make contactwith icons 702, 704, 706, 708, or 710 to launch a correspondingapplication. Launching an application means causing the application torun in the foreground of device 600 and to appear on touchscreen 604.

Icon 706 corresponds to a remote control application. A remote controlapplication allows a user to remotely control other electronic devices.These other electronic devices can be referred to as target electronicdevices. Target electronic devices are capable of being remotelycontrolled, meaning that they have the requisite hardware and/orsoftware to receive and act on instructions from remote controllers.Some target electronic devices, however, may not always be responsive toremote control even if they are capable. For example, a targetelectronic device may be configured to receive and process incominginstructions when it is running some software applications but notothers. Such a target electronic device may be identified as responsiveto remote control when it is executing logic (e.g., a target softwareapplication) that has an operation that can be initiated remotely (e.g.,from device 600). In some cases, a target electronic device isresponsive to remote control when it is executing a relevant targetsoftware application in the foreground, but not be responsive to remotecontrol when the target software application is executing in thebackground. Device 600 may require an external electronic device to beregistered with device 600 before it is treated as a target electronicdevice capable of remote communication. The registration process may beakin to “pairing” processes used in the context of Bluetooth™communication, WiFi Protected Setup (WPS), operating system devicesetup, and the like.

In some examples, electronic device 600 may determine responsiveness bylistening for network discovery information broadcasted by targetelectronic devices that are responsive to remote control. In theseexamples, electronic device 600 expects target electronic devices thatare responsive to remote control to send out communication datagrams(e.g., using a service discovery protocol) indicating their presence andresponsiveness onto a communication channel (e.g., a network). In someexamples, electronic device 600 may determine responsiveness by sendingrequests onto a communication channel and listening for acknowledgementsfrom target electronic devices that are responsive to remote control. Inthese examples, electronic device 600 expects target electronic devicesthat are responsive to remote control to acknowledge requests.Electronic device 600 may broadcast requests and/or target requests toregistered electronic devices. In some examples, electronic device 600may determine responsiveness using a combination of the above-describedtechniques. For example, electronic device 600 may actively poll fortarget electronic devices by sending broadcast signals when its batterylevel is relatively full (e.g., above a threshold), but passively listenfor network discovery data from target electronic devices when itsbattery level is relatively empty (e.g., below a threshold).

A user may make contact with icon 706 to launch the remote controlapplication. This causes device 600 to display one of several possiblegraphical user interface screens (e.g. landing screen). In someexamples, when a user activates icon 706, device 600 identifies whetherthere is a registered target electronic device that is currentlyresponsive to remote control. If so, device 600 displays a screendepicting possible operations of the identified target electronicdevice. One example of a target electronic device that is responsive toremote control is a media player that is currently playing media. FIG. 8shows an exemplary screen for controlling such a media player. Screen800 has graphical user interface objects 802, 804, and 806 representingoperations on a target electronic device that has been identified asbeing responsive to remote control. User interface object 802 representsa “pause” operation, object 804 represents a “fast forward” operation,and object 806 represents a “rewind” operation. These operationsconstitute transport operations. When a user contacts object 802, forexample, device 600 sends data representing an instruction to the mediaplayer instructing it to pause. Screen 800 may additionally includeother objects representing additional transport operations (e.g.,“play,” “stop,” “next,” “previous,” and so forth). In some examples,user interface object 802 (representing pause) may be replaced with auser interface object representing play after being invoked.

Another example of a target electronic device that is responsive toremote control is a computer that is running a presentation program,such as Microsoft™ PowerPoint or Apple™ KeyNote. In some examples, theremote control application prioritizes the display of remote controlsfor presentation programs. Restated, if two target devices areresponsive to remote control, and one of the two target devices isrunning a presentation program, the remote control application may landon remote controls for the presentation program upon launch.

Device 600 can display other landing screens. When a user activates icon706 (FIG. 7), device 600 may be unable to identify any registered targetelectronic device that is currently responsive to remote control. Insome examples, when this occurs, device 600 may display a screen thatcorresponds to the last target electronic device that was remotelycontrolled using device 600, even if that target electronic device isnot currently responsive. In other examples, when this occurs, device600 may display a screen that corresponds to the last media playbackdevice that was remotely controlled using device 600, even if thattarget media device is not currently responsive.

In yet other examples, when this occurs, device 600 may display agraphical user interface screen permitting a user's selection of atarget electronic device (from a list of devices) to control remotely.FIG. 9 shows an example of such a screen. Screen 900 has graphical userinterface objects 402, 404, and 406. These graphical user interfaceobjects correspond to electronic devices that are capable of beingremotely controlled and have been registered with device 600. Object 902is related to a set-top media playback device, object 904 is related toan audio player, and object 906 is related to an automobile. A user canactivate one of these objects to view the remotely controllableoperations of the corresponding target electronic device. For example, auser can make contact with object 904 to view transport operations forthe corresponding audio player. When a user contacts object 904, device600 may display screen 800 (FIG. 8), in some examples.

Device 600 can display still other landing screens. In some examples,when a user activates icon 706 (FIG. 7) and device 600 determines thatno registered target electronic device is currently responsive to remotecontrol, then device 600 may display a screen for registering targetelectronic devices (instead of screen 900 as shown in FIG. 9). Thepossibility of this alternate behavior means that device 600 can responddifferently when it is (i) unable to detect a responsive electronicdevice, as opposed to when it (ii) detects affirmatively that nearbyregistered electronic devices exist but are not responding to remotecontrol instructions. More specifically, device can display screen 900(FIG. 9) when (i) occurs but display a device registration screen when(ii) occurs. This distinction is especially relevant if targetelectronic devices can execute multiple software applications. Suchtarget electronic devices may be responsive to remote control whencertain applications are running, but be unresponsive to remote controlat other times. Device 600 can thus react accordingly, meaning that insome examples device 600 avoids asking a user to register additionaltarget electronic devices simply because his registered targetelectronic devices are momentarily unresponsive to remote control.

Returning to FIG. 9, a user may make contact with graphical userinterface object 902 to see operations of the corresponding media playerthat can be controlled remotely. FIG. 10 depicts graphical userinterface screen 1000 showing the remote-controllable operations of themedia player. The relevant media player may be a set-top media device orother device. Screen 1000 includes graphical user interface objects1002, 1004, and 1006 representing transport operations. A user maycontact object 504, for example, to fast-forward into the mediaplayback. Screen 1000 also includes text (e.g., affordances) identifyingthe media being played.

As can be seen from the exemplary user interfaces screens of 800 (FIG.8) and 1000 (FIG. 10), device 600 can share graphical user interfaceobjects between different screens of its remote control application. Insome examples, the sharing of graphical user interface objects refers tothe re-use of graphical user interface objects to cause the same effectamong different user interface screens of target electronic devices.That is, graphical user interface objects 802 (FIG. 8) and 1002 (FIG.10) are shared in that they have the same visual appearance and the sameeffect of pausing playback on different electronic devices. In someexamples, the sharing of remote control components refers to the abilityof one graphical user interface object to concurrently cause the sameeffect across multiple target electronic devices. That is, graphicaluser interface object 1002 can have the effect of pausing playback onmultiple set-top devices that are registered with device 600 in responseto a single user contact, such as multiple living room cable boxes.

Device 600 can display yet still other landing screens. In someexamples, when a user activates icon 706 (FIG. 7), device 600 maydetermine the positioning of nearby target electronic devices. Device600 may then display graphical representations of nearby targetelectronic devices based on their relative positions and/or proximities.For example, device 600 may determine that a first target electronicdevice is in front of the user and a second target electronic device isto the left of the user. In this situation, device 600 may display afirst icon representing the first target electronic device near the topof touchscreen 604 and a second icon representing the second targetelectronic device near the left of touchscreen 604. FIG. 11 illustratesexemplary graphical user interface screen 1100 in which graphical userinterface objects representing different target electronic devices arepositioned and sized on-screen according to their positions andproximities with respect to device 600.

As background, car 1110, cellular phone 1112, and door entry system 1114are nearby and are positioned to the north, east, and west of device600, respectively. Car 1110 is physically closest to device 600 whilecellular phone 1112 is farthest away. In view of these positions andproximities, device 600 displays screen 1100 having graphical userinterface object 1106 (representing car 1110) near the top edge oftouchscreen 1104, object 1102 (representing cellular phone 1112) nearthe right edge, and object 1104 (representing door entry system 1114)near the left edge. In other words, in some examples, the on-screenposition of a graphical user interface object corresponds to therelative position of its corresponding target electronic device withrespect to device 600. Device 600 also displays object 1106 in largersize as compared with icon 1102. In some examples, the on-screen size ofa graphical user interface object is inversely proportional to thedistance between device 600 and its corresponding target electronicdevice.

Note, while distance can be measured using physical units, in someexamples, distance between devices may be approximated based onmeta-data such as network access delays and GPS location information,for example.

Device 600 can display yet still other landing screens. In someexamples, when a user activates icon 706 (FIG. 7), device 600 groupstarget electronic devices into categories and display a listing ofdevice categories. This grouping is useful when the number of registeredtarget electronic devices exceeds that which can be usefully displayedon touchscreen 604. In some examples, this limit is based on apredetermined numeric threshold. In some examples, particularly wheretouch input is used, graphical user interface objects that are smallerthan the tip of the average human index finger are considered not usefulfor touch input. FIG. 12 shows exemplary graphical user interface screen1200. Screen 1200 has graphical user interface objects 1202, 1204, and1206 indicating the categories of “home,” “personal portable devices,”and “automotive,” respectively. A user may make contact with object 1202to view a more detailed listing of target electronic devices related tohome automation, such as media playback devices, door entry devices,lighting devices, and so forth. A user may contact object 1204 to view amore detailed listing of target electronic devices such as portablemusic players and cellular phones, for example. A user may contactobject 1206 to view a more detailed listing of target electronic devicesrelated to in-car telematics systems.

Turning to FIG. 13, in response to activation of graphical userinterface object 1202 (FIG. 12), device 600 displays graphical userinterface screen 1300. Screen 1300 includes user interface objects 1302,1304, and 1306 corresponding to target electronic devices in the Homecategory: User interface object 1302 corresponds to a television remotecontrol, user interface object 1304 corresponds to a garage door opener,and user interface object 1306 corresponds to a remote lightingcontroller. A user may activate user interface object 1302, 1304, or1306 to launch remote control screens for these target electronicdevices.

In some examples, device 600 may be able to detect motion thatrepresents a raise gesture. For example, if device 600 is a wearabledevice configured to be worn on a user's arm, the device may be able todetect when the user has raised his arm. When a raise gesture isdetected, device 600 may send an instruction that instructs a targetelectronic device to perform an operation, or to stop the performance ofan operation. For example, device 600 may instruct a media playbackdevice to stop (or pause) playback when a user raises the device.Techniques for determining raising gestures such as wrist raises aredescribed in, e.g., U.S. Provisional Patent Application Ser. No.62/026,532, “Raise Gesture Detection in a Device,” filed Jul. 18, 2014,the content of which is hereby incorporated by reference. In addition,device 600 may display user interface object representing additionalcontrols (e.g., transport controls) for the target electronic device.

Device 600 can display user interface screen based on the intensity ofcontacts being applied to touchscreen 604 (FIG. 6). Specifically, device600 can respond differently when a user contacts touchscreen 604 ofdevice 600 with a greater intensity than what is normally needed toactivate a graphical user interface object. This aspect is describedwith reference to FIGS. 22A-B. As shown in FIG. 22A, device 600 maydisplay user interface screen 2200. Screen 2200 may be screen 800 (FIG.8) for remotely controlling a target electronic device, in this instancean audio player. A user may activate (e.g., tap) a displayed icon toinvoke a corresponding transport control of the target audio player. Insome examples, if the intensity of the user's contact (e.g., tap 2208)on icon 2204 (or more generally touchscreen 604) exceeds a thresholdintensity, device 600 may, instead of invoking a corresponding remoteoperation of the target electronic device, replace the display of screen2200 with a graphical user interface screen 2210 showing alternatefeatures of the target electronic device. For example, as shown in FIG.22B, screen 2210 include shuffling playback icon 2212, repeatingplayback icon 2214, and/or playlist and/or station icon 2216. Thesefeatures constitute alternate features. More generally, the term“alternate features” refers to features different from those featuresotherwise displayed on device 600 had the intensity of contact 2208 beenbelow the threshold intensity (e.g., features corresponding to screen2200).

2. Registering Electronic Devices

As discussed above, device 600 may require registration of an electronicdevice before allowing remote control of the electronic device. Whenthis is the case, device 600 provides graphical user interface screensfor registering target electronic devices. In some examples, device 600proactively displays the necessary registration screens under some usageconditions, as discussed above.

In some examples, device 600 reactively displays the necessaryregistration screens when a user contacts touchscreen 604 of device 600with a greater intensity than what is normally needed to activate agraphical user interface object. When the intensity sensors of device600 detect a contact that has a maximum intensity that is greater than athreshold intensity, device 600 can display graphical user interfacescreens for registering electronic devices as target electronic devices.This aspect is described with reference to FIGS. 21A-B. In FIG. 21A,device 600 is displaying user interface screen 2100 which may be screen900 (FIG. 9) for selecting a target electronic device to remote control.A user may activate (e.g., tap) on a displayed graphical user interfaceobject to select a corresponding electronic device that is to beremotely controlled. In some examples, if the intensity of the user'scontact (e.g., tap 2108) on icon 2106 (or more generally touchscreen604) exceeds a threshold intensity, device 600 may, instead ofdisplaying remote controls for the corresponding electronic device,replace the display of screen 2100 with graphical user interface screen2110. Screen 2110, as shown, provides an alternate feature ofregistering new target electronic devices.

Device 600 may limit what electronic devices can be registered as targetelectronic devices. In some examples, device 600 registers only nearbyelectronic devices. Device 600 may consider an electronic device to be“nearby” if the two are within the communication range of a short-rangewireless communication protocol such as Bluetooth™ (whether classic orlow energy), near-field communication, ZigBee™, and the like. Also,device 600 may consider an electronic device to be “nearby” if the twoare within communication range of a local area network such as IEEE802.11 network. Also, device 600 considers an electronic device to be“nearby” if the two are within communication range of a wide areanetwork such as a cellular network, a cellular data network, or a widearea network (e.g., internet). Also, device 600 may consider networkresponse times between itself and a target electronic device indetermining whether the target electronic device is nearby. Also, device600 may consider additional meta-data, such as GPS location information,in determining whether a target electronic device is nearby.

In some examples, in response to a user contact at a maximum intensitythat is greater than the predetermined threshold intensity, device 600displays a user interface for viewing and changing configurationsettings associated with the remote control application.

3. Progressive Disclosure

FIG. 14A shows graphical user interface screen 1400, which can be analternative to screen 700 (FIG. 7) in some examples. As shown, screen1400 includes graphical user interface object 1402 corresponding to aremote control application. Screen 1400 also includes affordance 1406indicating additional information related to the remote controlapplication. Affordance 1406 may appear inside graphical user interfaceobject 1402 (as shown), or may appear outside but adjacent to graphicaluser interface object 1402 (not shown). Exemplary affordances can show,for example, (i) whether at least one registered electronic device isresponsive to remote control; (ii) the types and/or number of registeredelectronic devices responsive to remote control; (iii) the types and/ornumber of electronic devices capable of remote control; (iv) the typesand/or number of electronic devices capable of remote control andavailable for registration with device 600; and/or (iv) the types and/ornumber of electronic devices registered with device 600. Theseaffordances can range from a simple visual indicator (such as an image)to rows of text (such as scrolling/marquee text).

Affordance 1402 need not always be displayed. As demonstrated by FIG.14B, in some examples, affordance 1402 disappears when graphical userinterface object 1406 is reduced in size. Object 1406 may become reducedin size when a user zooms-out from screen 1400 using one or more of theinput mechanisms of device 600, for example. Suitable input mechanismsmay include one or more of the touchscreen(s), button(s) and rotatablemechanism described above. Restated, affordance 1402 may be displayed inone graphical user interface screen at one zoom level (e.g., screen1400) but not on another screen at another zoom level (e.g., screen1410).

4. Processes for Remotely Controlling a Target Electronic Device

FIG. 15A depicts exemplary process 1500 that device 600 can perform tocontrol a target electronic device. At block 1510, a graphical userinterface object is displayed on a touchscreen. The graphical userinterface object represents a remote control application for remotelycontrolling a target electronic device. At block 1520, data representinga contact input such as a finger tap is obtained. A determination ismade that the contact occurred on the user interface object representingthe remote control application. In response to the determination thatthe received data represents a relevant contact, at block 1530, anelectronic device that can be remotely controlled is identified. Theidentified target electronic device may have been registered on device600. If the identified target electronic device is determined to bepresently responsive to remote control, processing proceeds to block1540, where graphical user interface objects for controlling theidentified target electronic device are displayed. The displayedgraphical user interface objects may depend on the operations supportedby the identified target electronic device. If no target electronicdevice is identified, processing proceeds to block 1550, where graphicaluser interface objects for manually selecting a target electronic devicefor remote control are displayed.

FIG. 15B depicts exemplary process 1560 that device 600 can perform tocontrol a target electronic device. At block 1565, a graphical userinterface object is displayed on a touchscreen. The graphical userinterface object includes a plurality of icons including an icon thatrepresents a remote control application for remotely controlling atarget electronic device. At block 1570, a first contact on atouch-sensitive display is received at the location of the icon. Atblock 1575, a determination is made as to whether a target device out ofa plurality of target devices is responsive to remote control. Inresponse to the first contact and a determination that the target deviceis responsive to remote control, at block 1580, a first plurality ofremote controls for the target device is displayed. At block 1585, whiledisplaying the first plurality of remote controls, a second contact onthe touch-sensitive display is received. The second contact has amaximum intensity in some examples. At block 1590, in response to thesecond contact and a determination that the maximum intensity is below athreshold intensity, the target device is instructions to perform anoperation. At block 1595, in response to the second contact and adetermination that the maximum intensity is above the thresholdintensity, a second plurality of remote controls for the first targetdevice is displayed.

The identified target electronic device may have been registered ondevice 600. If the identified target electronic device is determined tobe presently responsive to remote control, processing proceeds to block1540, where graphical user interface objects for controlling theidentified target electronic device are displayed. The displayedgraphical user interface objects may depend on the operations supportedby the identified target electronic device. If no target electronicdevice is identified, processing proceeds to block 1550, where graphicaluser interface objects for manually selecting a target electronic devicefor remote control are displayed.

FIG. 16 depicts exemplary process 1600 that device 600 can perform tocontrol a target electronic device. At block 1610, informationrepresenting multiple target electronic devices is obtained. Theobtained information may be used to identify target electronic devicesthat are responsive to remote control. At block 1620, a user interfaceobject is displayed on touchscreen 604. The user interface object mayrepresent a remote control application for remotely controlling a targetelectronic device. At block 1630, data representing a contact, such as afinger tap, on the user interface object is received. At block 1640, adetermination is made as to whether the number of target electronicdevices that may be remotely controlled exceeds a threshold. Thisdetermination may be based on the information obtained at block 1610. Ifthe number of devices is determined to exceed the threshold, thenprocessing proceeds to block 1650 where graphical user interface objectsrepresenting categories of target electronic devices are displayed. Ifthe number of devices is determined not to exceed the threshold, thenprocessing proceeds to block 1660 where graphical user interface objectsrepresenting target electronic devices are displayed.

FIG. 17 depicts exemplary process 1700 that device 600 can perform toidentify target electronic devices for remote control. At block 1710,the location of a target electronic device is determined. The locationof the target electronic device relative to device 600 may be determinedby obtaining network and/or location information from the targetelectronic devices, for example. At block 1720, a user interface objectrepresenting the target electronic device is displayed on touchscreen604. The user interface object may be displayed at a location ontouchscreen 604 that illustrates the location of the target electronicdevice relative to device 600, as discussed above with respect to FIG.6.

FIG. 18A depicts exemplary process 1800 that device 600 can perform toindicate whether target electronic device are available for remotecontrol. At block 1810, a relative larger number (as compared with block1830) of graphical user interface objects are displayed on touchscreen604. The displayed graphical user interface objects include an objectrepresenting a remote control application. At block 1820, datarepresenting a user input is obtained form an input device of device600. A determination is made that the received data represents a zoom-inoperation. In response to the determination that the received datarepresents a zoom-in operation, at block 1830, a reduced number (ascompared with block 1810) of graphical user interface objects aredisplayed on touchscreen 604. The displayed graphical user interfaceobjects still include the object representing the remote controlapplication being displayed in a relatively larger size (as comparedwith block 1810). Additionally, the object representing the remotecontrol application includes an additional affordance. The additionalaffordance may indicate, for example: (i) whether at least oneregistered electronic device is responsive to remote control; (ii) thetypes and/or number of registered electronic devices responsive toremote control; (iii) the types and/or number of electronic devicescapable of remote control; (iv) the types and/or number of electronicdevices capable of remote control and available for registration withdevice 600; and/or (iv) the types and/or number of electronic devicesregistered with device 600.

FIG. 18B depicts exemplary process 1850 that device 600 can perform toindicate whether target electronic device are available for remotecontrol. At block 1860, a relative larger number (for example, ascompared with block 1880) of graphical user interface objects aredisplayed on touchscreen 604. The displayed graphical user interfaceobjects include an object (e.g., icon) representing a remote controlapplication. At block 1870, data representing a first movement of arotatable input device is received. In response to the receiving thedata representing the first movement, at block 1880, a reduced number(as compared with block 1860) of graphical user interface objects aredisplayed on touchscreen 604. The displayed graphical user interfaceobjects still include the object representing the remote controlapplication being displayed in a relatively larger size (as comparedwith block 1860). At block 1890, an additional affordance is displayed.The additional affordance may indicate, for example: (i) whether atleast one nearby electronic device is responsive to remote control; (ii)the types and/or number of nearby electronic devices responsive toremote control; (iii) the types and/or number of electronic devicescapable of remote control; (iv) the types and/or number of electronicdevices capable of remote control and available for registration withdevice 600; and/or (iv) the types and/or number of electronic devicesregistered with device 600.

FIG. 24 depicts exemplary process 2400 that device 600 can perform tocontrol a target device. At block 2410, a plurality of iconsrepresenting applications, including an icon representing a remotecontrol application, are displayed. At block 2420, data representinguser input is obtained from an input device of device 600. Adetermination is made that the received data represents a touch at aposition of the icon representing the remote control application. Atblock 2430, a target device that is responsive to remote control isidentified from a larger plurality of target devices. At block 2440, araise gesture is detected based on motion of the electronic devicedetected by a motion sensor. At block 2450, in response to detecting theraise gesture, an instruction is sent to the target device instructingthe target device to perform an operation.

In some examples, the instruction is an instruction to stop (or pause)an operation on the target device. For example, device 600 may instructa media player to stop (or pause) playback in response to a raisegesture. In some examples, blocks 2430-2450 are performed only if blocks2410-2420 are performed, meaning that an electronic device would sendremote control instructions only the user has launched the remotecontrol application by touching a corresponding icon. In some examples,blocks 2430-2450 are performed even if blocks 2410-2420 are notperformed, meaning that an electronic device may send remote controlinstructions based on raise gestures even if the user has not launchedthe remote control application. Techniques for detecting a raise gestureinvolving an electronic device may include those described in U.S.Provisional Patent Application Ser. No. 62/026,532, “Raise GestureDetection in a Device,” filed Jul. 18, 2014, the content of which ishereby incorporated by reference.

5. Computing Systems

FIG. 19 depicts exemplary computing system 1900 that, in some examples,supports device 600. Computing system 1900 has bus 1902 that operativelycouples I/O section 1904 with one or more computer processors 1906 andmemory 1908. I/O section 1904 can be connected to display 1910, whichcan have touch-sensitive component 1912 and, optionally, touch-intensitysensitive component 1930. In addition, I/O section 1904 can be connectedwith communication unit 1918 for receiving application and operatingsystem data, using Wi-Fi, Bluetooth™, near field communication (“NFC”),cellular and/or other wireless communication techniques. Computingsystem 1900 can include input mechanisms 1914 and/or 1916. Inputmechanism 1914 may be a rotatable input device, for example. Inputmechanism 1916 may be a button, for example. Computing system 1900 caninclude various sensors, such as GPS sensor 1920, accelerometer 1922,directional sensor 1924 (e.g., compass), gyroscope 1926, motion sensor1928, and/or a combination thereof, all of which can be operativelyconnected to I/O section 1904.

Memory 1908 of computing system 1900 can be a non-transitory computerreadable storage medium, for storing computer-executable instructions,which, when executed by one or more computer processors 1906, forexample, can cause the computer processors to perform the remote controltechniques described above, including processes 1500-1850 (FIGS.15A-18B) and process 2400 (FIG. 24). The computer-executableinstructions can also be stored and/or transported within anynon-transitory computer readable storage medium for use by or inconnection with an instruction execution system, apparatus, or device,such as a computer-based system, processor-containing system, or othersystem that can fetch the instructions from the instruction executionsystem, apparatus, or device and execute the instructions. For purposesof this document, a “non-transitory computer readable storage medium”can be any medium that can tangibly contain or store computer-executableinstructions for use by or in connection with the instruction executionsystem, apparatus, or device. The non-transitory computer readablestorage medium can include, but is not limited to, magnetic, optical,and/or semiconductor storages. Examples of such storage include magneticdisks, optical discs based on CD, DVD, or Blu-ray technologies, as wellas persistent solid-state memory such as flash, solid-state drives, andthe like. Computing system 1900 is not limited to the components andconfiguration of FIG. 19, but can include other or additional componentsin multiple configurations.

FIG. 23 shows exemplary functional blocks of an electronic device 2300that, in some examples, perform the features described above. As shownin FIG. 23, an electronic device 2300 includes a display unit 2302configured to display graphical objects; a touch-sensitive surface unit2304 configured to receive user gestures; one or more sensor units 2306configured to detect intensity of contacts with the touch-sensitivesurface unit; and a processing unit 2308 coupled to the display unit23002, the touch-sensitive surface unit 2304, and the sensor units 2306.In some examples, the processing unit includes a detecting unit 2310, aremote control unit 2312, and a communication unit 2314. The functionalblocks of the device 2300 are, optionally, implemented by hardware,software, or a combination of hardware and software to carry out theprinciples of the various described examples. It is understood bypersons of skill in the art that the functional blocks described in FIG.23 are, optionally, combined or separated into sub-blocks to implementthe principles of the various described examples. Therefore, thedescription herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein. In some examples, processing unit 2308 is configured to detect acontact (e.g., with the detecting unit 2310), on the touch-sensitivesurface unit 2304 over a graphical user interface object; and inresponse to detecting the contact, instruct a target electronic deviceto perform an operation. The instruction may be transmitted usingcommunication unit 2314.

In some examples, processing unit 2308 is configured to detect a contact(e.g., with the detecting unit 2310), on the touch-sensitive surfaceunit 2304 over a graphical user interface object; and in response todetecting the contact: in accordance with a determination that thecontact is below a predefined intensity criteria, perform a firstoperation (e.g., display a default set of remote control operations)using remote control unit 2312; and in accordance with a determinationthat the contact is above the predefined intensity criteria, perform adifferent second operation (e.g., display an alternate set of remotecontrol operations).

In some examples, processing unit 2308 is configured to detect a contact(e.g., with the detecting unit 2310), on the touch-sensitive surfaceunit 2304 over a graphical user interface object. In addition,communication unit 2314 is configured to detect nearby target electronicdevices. In response to detecting the contact and based on informationabout nearby target electronic device, device 2300 can display ondisplay unit 2302 a plurality of graphical user interface objectsrepresenting the nearby target electronic devices. The on-screenlocation of the graphical user interface units can reflect the relativelocation of the nearby target electronic devices with respect to device2300.

6. Remote Control Via Intermediate Device

The availability of components in system 1900, particularly short andlong range communication interfaces, may affect the operation of device600. In some examples, a target electronic device may use acommunication protocol not supported by device 600. For example, thetarget electronic device may support WiFi but not Bluetooth™, whiledevice 600 may support Bluetooth™ but not WiFi. In this situation,device 600 may use an intermediate device that supports both Bluetooth™and WiFi protocols to communicate with the target electronic device. Theintermediate device may be a Bluetooth™ and WiFi-enabled cellular phone,for example.

FIG. 20 depicts an exemplary communication path between device 600,intermediate device 2002, and target electronic device 2004. Device 600communicates with intermediate device 2002 using a first communicationprotocol that may not be supported by target electronic device 2004, andintermediate device 2002 relays that communication to target electronicdevice 2004 using a second communication protocol that is supported bytarget electronic device 2004. The reverse communication path may alsobe supported, meaning that target electronic device 2004 can communicatewith device 600 via intermediate device 2002.

Communications sent to target electronic device 2004 may includeinstructions that cause the target electronic device to perform anoperation. In some examples, intermediate device 2002 relays aninstruction from device 600 to target electronic 2004 verbatim. In someexamples, intermediate device 2002 processes an instruction from device600 and creates a corresponding instruction for transmission to targetelectronic device 2004. In some examples, intermediate device 2002modifies an instruction from device 600 and transmits the modifiedinstruction to target electronic device 2004. Note, in some examples,the communication path depicted by FIG. 20 can be utilized even ifdevice 600 and target electronic device 2004 support a commoncommunication protocol. In these examples, the communication pathdepicted in FIG. 20 may be preferred by device 600 because intermediatedevice 2002 contains data relevant to the remote control operation.Also, in these examples, the datagrams sent by device 600 tointermediate device 2002 need not be identical to the datagrams sent byintermediate device 2002 to target electronic device 2004, meaning that,in “relaying” an instruction, intermediate device 2002 may create a newinstruction datagram for transmission to target electronic device 2004based on an instruction datagram received from device 600.

In accordance with some embodiments, FIG. 25 shows an exemplaryfunctional block diagram of an electronic device 2500 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2500 are configured to perform the techniques described above.The functional blocks of the device 2500 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 25 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 25, an electronic device 2500 includes atouch-sensitive display unit 2502 configured to detect the intensity ofcontacts with the touch-sensitive display unit 2502 and optionally oneor more sensor units 2522 and a tactile output unit 2524. The one ormore sensor units 2522 may be configured to detect the intensity ofcontacts, for instance, with the touch-sensitive display 2522 and/or thetouch-sensitive display unit 2502 and the tactile output unit 2524 maybe configured to provide haptic outputs, for instance, in response touser inputs. The electronic device 250 further may include a processingunit 2504 coupled to the touch-sensitive display unit 2502, the one ormore sensor units 2522, and the tactile output unit 2524. In someembodiments the processing unit 2504 includes one or more of a displayenabling unit 2506, a receiving unit 2508, a determining unit 2510, anidentifying unit 2512, an invoking unit 2514, a sending unit 2516, and atransmitting unit 2518.

In some embodiments, the processing unit 2504 is configured to: enabledisplay (e.g., with the display enabling unit 2506) of a plurality oficons representing applications, including an icon representing a remotecontrol application; receive (e.g., with the receiving unit 2508) afirst contact on the touch-sensitive display at a location of the icon;determine (e.g., with the determining unit 2510) whether a target deviceout of a plurality of target devices is responsive to remote control.The processing unit 2504 is further configured to, in response to thefirst contact and a determination of the target device being responsiveto remote control: enable display (e.g., with the display enabling unit2506) of a first plurality of remote controls for the target device;while enabling display of the first plurality of remote controls,receive (e.g., with the receiving unit 2508) of a second contact on thetouch-sensitive display, the second contact having a maximum intensity;in response to receiving the second contact and a determination that themaximum intensity is below a threshold intensity, instruct the targetdevice to perform an operation; and in response to receiving the secondcontact and a determination that the maximum intensity is above thethreshold intensity, enable display (e.g., with the display enablingunit 2506) of a second plurality of remote controls for the first targetdevice.

In some embodiments, the processing unit 2504 is configured to: enabledisplay (e.g., with the display enabling unit 2506) of a user interfaceobject on the touch-sensitive display of the electronic device, whereinthe displayed user interface object represents a remote controlapplication; receive data (e.g., with the receiving unit 2508)representing a selection on the displayed user interface object;identify (e.g., with the identifying unit 2512) a target device, out ofa plurality of target devices, that is responsive to remote control; andin response to receiving the data representing the selection, enabledisplay (e.g., with the display enabling unit 2506) of a plurality ofgraphical user interface objects for controlling operations of theidentified target device.

In some embodiments, the processing unit 2504 is further configured to:in response to an identification that no target device is responsive toremote control, enable display (e.g., with the display enabling unit2506) of a plurality of graphical user interface objects representingthe plurality of target devices.

In some embodiments, the touch-sensitive display unit includes one ormore sensor units to detect the intensity of contacts with thetouch-sensitive display, the data representing the selection is a firstdata, the target device is a first target device. The processing unit isfurther configured to: receive (e.g., with the receiving unit 2508)second data representing a second contact at a location on thetouch-sensitive display, the second contact having a maximum intensityabove a threshold intensity; and in response to the second contact,invoke (e.g., with the invoking unit 2514) a user interface forregistering a second target electronic device with the electronicdevice.

In some embodiments, the touch-sensitive display unit includes one ormore sensor units to detect the intensity of contacts with thetouch-sensitive display, the data representing the selection is a firstdata, the target device is a first target device. Further, theprocessing unit 2504 is further configured to: receive (e.g., with thereceiving unit 2508) second data representing a second contact at alocation on the touch-sensitive display, the second contact having amaximum intensity below a threshold intensity, the location associatedwith an operation of the first target device; in response to the secondcontact, send (e.g., with the sending unit 2516) an instruction to thetarget device instructing the target device to perform the operation;receive (e.g., with the receiving unit 2508) third data representing athird contact on the display, the third contact having a maximumintensity above the threshold intensity; and in response to the thirdcontact, enable display (e.g., with the display enabling unit 2506) of auser interface for registering a second target device with the remotecontrol application.

In some embodiments, the data representing the selection is a firstdata. Further, the processing unit 2504 is further configured to: send(e.g., with the sending unit 2516), from the electronic device to anintermediate electronic device, data representing an instructioninstructing the target device to perform the operation, and theinstruction is communicated by the intermediate electronic device to thetarget device.

In some embodiments, the intermediate electronic device is a phone.

In some embodiments, the processing unit 2504 is configured to identify(e.g., with the identifying unit 2512) a target device by receivingnetwork service information sent by the target device.

In some embodiments, the processing unit 2504 is configured to identify(e.g., with the identifying unit 2512) the target device by transmitting(e.g., via a transmitting unit 2518) a request message and receiving(e.g., with the receiving unit 2508) an acknowledgement message sent bythe target device, wherein the acknowledge message was sent by thetarget device in response to the request message.

In some embodiments, the target device is responsive to remote controlwhen the target device is executing an application having an operationthat can be requested using the remote control application.

In some embodiments, the application executing on the target device isexecuting in the background.

In some embodiments, the target device is a device other than theelectronic device.

In some embodiments, the plurality of graphical user interface objectsincludes transport controls.

In some embodiments, the processing unit 2504 is configured to determine(e.g., with the determining unit 2510) the plurality of graphical userinterface objects based on the identified target device.

In some embodiments, the plurality of graphical user interface objectsis shared by the identified target device and at least one other deviceof the plurality of target devices.

The operations described above with reference to FIG. 15A are,optionally, implemented by components depicted in FIG. 1A-1B, 6, 19, 20,or 25. For example, displaying operations 1510, 1540, and 1550;receiving operation 1520; and identifying operation 1530 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 26 shows an exemplaryfunctional block diagram of an electronic device 2600 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2600 are configured to perform the techniques described above.The functional blocks of the device 2600 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 26 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 26, an electronic device 2600 includes atouch-sensitive display unit 2602, and a processing unit 2604 coupled tothe touch-sensitive display unit 2602. The processing unit 2604 includesan obtaining unit 2606, a display enabling unit 2608, a receiving unit2610, and a determining unit 2612.

The processing unit 2604 is configured to: obtain (e.g., with theobtaining unit 2606) data representing a plurality of target devices;enable display (e.g., with the display enabling unit 2608) of a userinterface object representing a remote control application; receive(e.g., with the receiving unit 2610) data representing a selection onthe displayed user interface object; and determine (e.g., with thedetermining unit 2612) whether the number of target devices exceeds athreshold; in accordance with a determination that the number exceedsthe threshold, enable display (e.g., with the display enabling unit2608) of a plurality of graphical user interface objects representingcategories of target devices, in response to receiving the data, and inaccordance with a determination that the number does not exceed thethreshold, enable display (e.g., with the display enabling unit 2608) ofa plurality of graphical user interface objects representing theplurality of target devices, in response to receiving the data.

The operations described above with reference to FIG. 16 are,optionally, implemented by components depicted in FIG. 1A-1B, 6, 19, 20,or 26. For example, obtaining operation 1610; displaying operations1620, 1650, and 1660; receiving operation 1630; and determiningoperation 1640 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 27 shows an exemplaryfunctional block diagram of an electronic device 2700 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2700 are configured to perform the techniques described above.The functional blocks of the device 2700 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 27 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 27, an electronic device 2700 includes atouch-sensitive display unit 2702, and a processing unit 2704 coupled tothe touch-sensitive display unit 2702. The processing unit 2704 includesa determining unit 2706, and a display enabling unit 2708.

The processing unit 2704 is configured to: determine (e.g., withdetermining unit 2706) the location of a target device relative to theelectronic device; and enable display (e.g., with display enabling unit2708), on the touch-sensitive display unit, of a user interface objectrepresenting the target device, the target device is nearby, and thedisplay position of the user interface object, on the touch-sensitivedisplay, is based on the location of the target device relative to theelectronic device.

In some embodiments, the processing unit 2704 is further configured toenable display (e.g., with the display enabling unit 2708) of the userinterface object on the top half of the touch-sensitive display unitwhen the location of the target device is in front of a user of theelectronic device.

In some embodiments, the processing unit 2704 is further configured todetermine (e.g., with the determining unit 2706) a distance between thetarget device and the electronic device and the processing unit isconfigured to enable display (e.g., with display enabling unit 2708) ofthe user interface object at a size that is inversely proportional tothe determined distance.

The operations described above with reference to FIG. 17 are,optionally, implemented by components depicted in FIG. 1A-1B, 6, 19, 20,or 27. For example, determining operation 1710 and displaying operation1720 are, optionally, implemented by event sorter 170, event recognizer180, and event handler 190. Event monitor 171 in event sorter 170detects a contact on touch-sensitive display 112, and event dispatchermodule 174 delivers the event information to application 136-1. Arespective event recognizer 180 of application 136-1 compares the eventinformation to respective event definitions 186, and determines whethera first contact at a first location on the touch-sensitive surface (orwhether rotation of the device) corresponds to a predefined event orsub-event, such as selection of an object on a user interface, orrotation of the device from one orientation to another. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally uses or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 28 shows an exemplaryfunctional block diagram of an electronic device 2800 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2800 are configured to perform the techniques described above.The functional blocks of the device 2800 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 28 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 28, an electronic device 2800 includes atouch-sensitive display unit 2802, optionally one or more sensor units2806 to detect the intensity of contacts, for instance, with thetouch-sensitive display, and a processing unit 2804 coupled to thetouch-sensitive display unit 2802 and, optionally, the one or moresensor units 2806. The processing unit 2804 includes a display enablingunit 2806, a receiving unit 2808 and a determining unit 2810.

The processing unit configured to: enable display (e.g., with displayenabling unit 2806) of a user interface object on the touch-sensitivedisplay of the electronic device, the displayed user interface objectrepresenting a remote control application; receive (e.g., with thereceiving unit 2808) first data representing a zoom function on thedisplayed user interface object; and in response to receiving the firstdata representing the zoom function, enable display of an affordanceincluding indication of nearby target devices capable of being remotelycontrolled.

In some embodiments, the indication indicates a number of nearby targetdevices capable of being remotely controlled.

In some embodiments, the processing unit 2804 is further configured to:receive (e.g., with the receiving unit 2808) second data representing asecond selection on the displayed affordance including indication ofnearby target devices; and in response to receiving the second datarepresenting the second selection, enable display (e.g., with displayenabling unit 2806) of a listing of the nearby target devices capable ofbeing remotely controlled.

In some embodiments, the processing unit 2804 is further configured to:receive (e.g., with the receiving unit 2808) third data representingselection of a target device from the listing of target devices; and inresponse to receiving the third data representing the selection of thetarget device, enable display (e.g., with display enabling unit 2806) ofa plurality of graphical user interface objects for controllingoperations of the selected target device.

In some embodiments, the plurality of graphical user interface objectsincludes transport controls.

In some embodiments, the plurality of graphical user interface objectsare determined based on the selected target device.

In some embodiments, the plurality of graphical user interface objectsare shared by the selected target device and at least one other devicein the listing of target devices.

In some embodiments, the processing unit 2804 is further configured to:in response to receiving the first data representing the first zoomfunction, determine (e.g., with the determining unit 2810) a number ofnearby target devices capable of being remotely controlled.

In some embodiments, the processing unit 2804 is further configured to:in response to a determination that no nearby target device is capableof being remotely controlled, enable display (e.g., with displayenabling unit 2806) of a plurality of graphical user interface objectsfor controlling operations on the last selected target device.

In some embodiments, the touch-sensitive display unit includes one ormore sensor units (e.g., sensor units 2810) to detect the intensity ofcontacts with the touch-sensitive display. The processing unit 2804 isfurther configured to: determine (e.g., with the determining unit 2810)the intensity of the third selection, wherein the third selection is acontact with the touch-sensitive display unit; in response to adetermination that the intensity of the third selection is greater thana predetermined threshold: enable display (e.g., with display enablingunit 2806) of a user interface for registering an additional targetdevice capable of being remotely controlled by the remote controlapplication; and in response to a determination that the intensity ofthe third selection is less than the predetermined threshold: enabledisplay (e.g., with display enabling unit 2806) of the listing of thenearby target devices capable of being remotely controlled.

In some embodiments, the processing unit 2804 is further configured to:receive (e.g., with the receiving unit 2808) data representing a fourthselection on the touch-sensitive display, wherein the fourth selectionis a contact on the touch-sensitive display; determine (e.g., with thedetermining unit 2810) the intensity of the fourth selection; and inresponse to a determination that the intensity of the fourth selectionis greater than the predetermined threshold: enable display (e.g., withthe display enabling unit 2806) of a user interface for viewing thesettings associated with the remote control application.

In some embodiments, the nearby target devices capable of being remotelycontrolled include target devices registered with the electronic device.

In some embodiments, the nearby target devices capable of being remotelycontrolled include target devices responsive to remote control.

In some embodiments, the nearby target devices capable of being remotelycontrolled include target devices accessible via a wirelesscommunications interface.

The operations described above with reference to FIG. 18A are,optionally, implemented by components depicted in FIG. 1A-1B, 6, 19, 20,or 28. For example, displaying operations 1810 and 1830 and receivingoperation 1820 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 29 shows an exemplaryfunctional block diagram of an electronic device 2900 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2900 are configured to perform the techniques described above.The functional blocks of the device 2900 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 29 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 29, an electronic device 2900 includes atouch-sensitive display unit 2902, a rotatable input device unit 2904;and a processing unit 2906 coupled to the touch-sensitive display unit2902 and the rotatable input device unit 2904. The processing unit 2906includes a display enabling unit 2908 and a receiving unit 2910.

The processing unit is configured to: enable display (e.g., with displayenabling unit 2908) of a plurality of graphical user interface objects,wherein a user interface object of the plurality of graphical userinterface objects is an icon representing a remote control application;receive (e.g., with receiving unit 2910) data representing a firstmovement of the rotatable input device; and in response to receiving thedata representing the first movement: enable display (e.g., with displayenabling unit 2908) of only a subset of the plurality of graphical userinterface objects, the displayed subset of graphical user interfaceobjects includes the icon representing the remote control application,and enable display (e.g., with display enabling unit 2908) of anaffordance including indication of nearby target devices capable ofbeing remotely controlled

In some embodiments, the affordance indicates a number of nearby targetdevices capable of being remotely controlled.

In some embodiments, the affordance is displayed within the iconrepresenting the remote control application.

The operations described above with reference to FIG. 18B are,optionally, implemented by components depicted in FIG. 1A-1B, 6, 19, 20,or 29. For example, display operations 1860, 1880, and 1890; andreceiving operation 1860 are, optionally, implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 30 shows an exemplaryfunctional block diagram of an electronic device 3000 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 3000 are configured to perform the techniques described above.The functional blocks of the device 3000 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 30 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 30, an electronic device 3000 includes atouch-sensitive display unit 3002, one or more sensor units 3004 todetect motion of the electronic device; and a processing unit 3006coupled to the touch-sensitive display unit 3002 and the or more sensorunits 3004. The processing unit 3006 includes one or more of anidentifying unit 3008, a detecting unit 3010, an instructing unit 3012,a display enabling unit 3014, and a receiving unit 3016.

The processing unit is configured to: identify (e.g., with theidentifying unit 3008) a target device that is responsive to remotecontrol out of a plurality of target devices; detect (e.g., with thedetecting unit 3010) a raise gesture based on detected motion of theelectronic device; and in response to detecting the raise gesture,instruct (e.g., with the instructing unit 3012) the target device toperform an operation.

In some embodiments, the processing unit is further configured to:enable display (e.g., with display enabling unit 3014) of a plurality oficons representing applications, including an icon representing a remotecontrol application; and receive (e.g., with receiving unit 3016) afirst contact on the touch-sensitive display at a location of the icon,where at least one of identifying the target device that is responsiveto remote control and detecting the raise gesture occurs after receivingthe first contact.

In some embodiments, instructing (e.g., with the instructing unit 3012)the target device includes instructing the target device to pause orstop an operation.

In some embodiments, instructing (e.g., with the instructing unit 3012)the target device includes instructing the target device to pause orstop playback of audio and/or visual content.

In some embodiments, identifying (e.g., with the identifying unit 3008)the target device that is responsive to remote control includesidentifying a target device that performs audio and/or visual playback.

In some embodiments, identifying (e.g., with the identifying unit 3008)the target device that is responsive to remote control includesidentifying a television or a television set-top media playback device.

In some embodiments, identifying (e.g., with the identifying unit 3008)a target device includes receiving network service information sent bythe target device.

In some embodiments, the processing unit 3010 is further configured to:enable display (e.g., with the display enabling unit 3014) of aplurality of graphical user interface objects for controlling operationsof the identified target device.

The operations described above with reference to FIG. 24 are,optionally, implemented by components depicted in FIG. 1A-1B, 6, 19, 20,or 30. For example, obtaining operation 1610; displaying operations1620, 1650, and 1660; receiving operation 1630; and determiningoperation 1640 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 31 shows an exemplaryfunctional block diagram of an electronic device 3100 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 3100 are configured to perform the techniques described above.The functional blocks of the device 3100 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 31 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 31, an electronic device 3100 includes atouch-sensitive display unit 3002, one or more sensor units 3004 todetect motion of the electronic device; and a processing unit 3006coupled to the touch-sensitive display unit 3102 and the or more sensorunits 3004. The processing unit 3106 includes one or more of a displayenabling unit 3108, a receiving unit 3110, a determining unit 3112, andan instructing unit 3116.

The processing unit 3106 is configured to display (e.g., with thedisplay enabling unit 3108) a plurality of icons representingapplications, including an icon representing a remote controlapplication; receive (e.g., with the receiving unit 3110) a firstcontact on the touch-sensitive display at a location of the icon;determine whether a target device out of a plurality of target devicesis responsive to remote control; in response to the first contact and adetermination of the target device being responsive to remote control:enable display (e.g., with the display enabling unit 3108) of a firstplurality of remote controls for the target device; while enablingdisplay of the first plurality of remote controls, receive (e.g., withthe receiving unit 3110) a second contact on the touch-sensitivedisplay, the second contact having a maximum intensity; in response toreceiving the second contact and a determination that the maximumintensity is below a threshold intensity, instruct (e.g., with theinstructing unit 3116) the target device to perform an operation; and inresponse to receiving the second contact and a determination that themaximum intensity is above the threshold intensity, enable display(e.g., with the display enabling unit 3108) of a second plurality ofremote controls for the first target device.

The operations described above with reference to FIG. 5B are,optionally, implemented by components depicted in FIG. 1A-1B, 6, 19, 20,or 30. For example, displaying operations 1565, 1580, 1595; receivingoperations 1570 and 1585; determining operation 1575, and instructingoperation 1590 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

What is claimed is:
 1. An electronic device, comprising: atouch-sensitive display; one or more processors; a memory; and one ormore programs, wherein the one or more programs are stored in the memoryand configured to be executed by the one or more processors, the one ormore programs including instructions for: determining the location of atarget device relative to the electronic device; and displaying, on thetouch-sensitive display, a user interface object representing the targetdevice, wherein the target device is nearby, and wherein the displayposition of the user interface object, on the touch-sensitive display,is based on the location of the target device relative to the electronicdevice.
 2. The electronic device of claim 1, wherein the user interfaceobject is displayed on the top half of the touch-sensitive display whenthe location of the target device is in front of a user of theelectronic device.
 3. The electronic device of claim 1, the one or moreprograms further including instructions for: determining a distancebetween the target device and the electronic device, wherein the size ofthe displayed user interface object is inversely proportional to thedetermined distance.
 4. A method, comprising: at an electronic devicewith a touch-sensitive display: determining the location of a targetdevice relative to the electronic device; and displaying, on thetouch-sensitive display, a user interface object representing the targetdevice, wherein the target device is nearby, and wherein the displayposition of the user interface object, on the touch-sensitive display,is based on the location of the target device relative to the electronicdevice.
 5. A non-transitory computer readable storage medium storing oneor more programs, the one or more programs comprising instructions,which when executed by one or more processors of an electronic devicewith a touch-sensitive display, cause the device to: determine thelocation of a target device relative to the electronic device; anddisplay, on the touch-sensitive display, a user interface objectrepresenting the target device, wherein the target device is nearby, andwherein the display position of the user interface object, on thetouch-sensitive display, is based on the location of the target devicerelative to the electronic device.